-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Clean up integrations page #29483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up integrations page #29483
Conversation
Preview links (active after the
|
|
Can we point to this section in the Github setup link? https://docs.datadoghq.com/internal_developer_portal/software_catalog/set_up/create_entities#github-integration |
|
Can we make the page title just "Integrations" |
hestonhoffman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small edit to please Vale, but LGTM!
Co-authored-by: Heston Hoffman <[email protected]>
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do? What is the motivation?
Was helping Dan out with changes he posted here - #29313 - but I ended up tweaking a lot so figured I'd create a fresh PR. What this does:
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes